Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07c0380c95b779b284e1cae66704ed3d62bad41fc35e330f81f9d13f8990a0de

Tx prefix hash: 57592bc57ec6954fde31759d1a0192b9f035cf4e2d23516655c753a36cb7fb85
Tx public key: 5dc4cfeda45c4748c3b8017f6ab1efd79dad83498be6f9d4f53b6e7e445c07e5
Timestamp: 1759214801 Timestamp [UCT]: 2025-09-30 06:46:41 Age [y:d:h:m:s]: 00:084:03:40:20
Block: 1379540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60254 RingCT/type: yes/0
Extra: 015dc4cfeda45c4748c3b8017f6ab1efd79dad83498be6f9d4f53b6e7e445c07e5021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5550e4ee964a25199a99938d33903ebfbfda59bcc6aab1d663323fa43d4b5939 0.600000000000 1867637 of 15

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": 1379550, "vin": [ { "gen": { "height": 1379540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5550e4ee964a25199a99938d33903ebfbfda59bcc6aab1d663323fa43d4b5939" } } ], "extra": [ 1, 93, 196, 207, 237, 164, 92, 71, 72, 195, 184, 1, 127, 106, 177, 239, 215, 157, 173, 131, 73, 139, 230, 249, 212, 245, 59, 110, 126, 68, 92, 7, 229, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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