Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6fc4ee54ddd044ad0e56e6e6d215badf2e905b523fa648b2a8f0bf6e8c0ca9d

Tx prefix hash: d241231d1058ecadc0607e9bbe7fd5f80ea9f47c597756304e8cba0416e23faf
Tx public key: 2873e9dc4187e9295407f3274ed4bea3938577ab248d4e086ff94bccefd290cc
Timestamp: 1697988534 Timestamp [UCT]: 2023-10-22 15:28:54 Age [y:d:h:m:s]: 01:092:21:27:38
Block: 875279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327587 RingCT/type: yes/0
Extra: 012873e9dc4187e9295407f3274ed4bea3938577ab248d4e086ff94bccefd290cc02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.772391253000 dcy

stealth address amount amount idx
00: 39553f51dae95772394753ee657f023908dd608c1dc28a535fd35131ac2dff45 0.772391253000 1330529 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": 875289, "vin": [ { "gen": { "height": 875279 } } ], "vout": [ { "amount": 772391253, "target": { "key": "39553f51dae95772394753ee657f023908dd608c1dc28a535fd35131ac2dff45" } } ], "extra": [ 1, 40, 115, 233, 220, 65, 135, 233, 41, 84, 7, 243, 39, 78, 212, 190, 163, 147, 133, 119, 171, 36, 141, 78, 8, 111, 249, 75, 204, 239, 210, 144, 204, 2, 17, 0, 0, 0, 4, 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