Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5f22f723d0a183bf0fa55953488abc1a13678aa51a3d7acd1d29e9211b0b5c

Tx prefix hash: 8ee04c69fd62a2884697c7d3bb49a6eda4cd99f3690457e7fc2b5ace84fb9378
Tx public key: 53d9d6b09ba281e510e7226f74b14a5b44742ba44da333c9fcf041db40f54449
Timestamp: 1728269262 Timestamp [UCT]: 2024-10-07 02:47:42 Age [y:d:h:m:s]: 01:038:04:44:27
Block: 1126112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285690 RingCT/type: yes/0
Extra: 0153d9d6b09ba281e510e7226f74b14a5b44742ba44da333c9fcf041db40f5444902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db3f25e42c34416138bd9c6d22925275303880d96672f7134e8d865b87cb1e10 0.600000000000 1608897 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": 1126122, "vin": [ { "gen": { "height": 1126112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db3f25e42c34416138bd9c6d22925275303880d96672f7134e8d865b87cb1e10" } } ], "extra": [ 1, 83, 217, 214, 176, 155, 162, 129, 229, 16, 231, 34, 111, 116, 177, 74, 91, 68, 116, 43, 164, 77, 163, 51, 201, 252, 240, 65, 219, 64, 245, 68, 73, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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