Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5352c30350484c5fd7bf08d3fe4b0c35657f81b985659a436486cad06d7122b6

Tx prefix hash: a145bbd049f09f71fbf902f55ed2d7c2c04e774f5f3006fc0c8eb3d1116ad468
Tx public key: f69f6f7cf4769da5a3b60b28cd5fceae59eae8e477556e2ab670258c1cf5f8f1
Timestamp: 1697900536 Timestamp [UCT]: 2023-10-21 15:02:16 Age [y:d:h:m:s]: 01:095:05:47:11
Block: 874547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329262 RingCT/type: yes/0
Extra: 01f69f6f7cf4769da5a3b60b28cd5fceae59eae8e477556e2ab670258c1cf5f8f102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.776716924000 dcy

stealth address amount amount idx
00: 250b971f0c8ea9d95e10f9f1e4d2dff97e50a56c2f69047d69f44245fb8526c9 0.776716924000 1329765 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 874557, "vin": [ { "gen": { "height": 874547 } } ], "vout": [ { "amount": 776716924, "target": { "key": "250b971f0c8ea9d95e10f9f1e4d2dff97e50a56c2f69047d69f44245fb8526c9" } } ], "extra": [ 1, 246, 159, 111, 124, 244, 118, 157, 165, 163, 182, 11, 40, 205, 95, 206, 174, 89, 234, 232, 228, 119, 85, 110, 42, 182, 112, 37, 140, 28, 245, 248, 241, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8