Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cda7decc11176996615dbf9ef6d6565026fddc68bacedb7fce70d009a1994253

Tx prefix hash: 2355931b9cd81389681440a4cd41fd22754dbcc6da92eaa3f713f818f1092f6e
Tx public key: 20a6be7fd35539d7f5389ab8c6e11b9baf903b0ecc674cd1961d9837a064c512
Timestamp: 1729469112 Timestamp [UCT]: 2024-10-21 00:05:12 Age [y:d:h:m:s]: 01:043:10:04:15
Block: 1136031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289449 RingCT/type: yes/0
Extra: 0120a6be7fd35539d7f5389ab8c6e11b9baf903b0ecc674cd1961d9837a064c5120211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45f7247876ebd631a9b45a593f5a66df9bf262a60ee814304593a6719ae5de43 0.600000000000 1619372 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": 1136041, "vin": [ { "gen": { "height": 1136031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45f7247876ebd631a9b45a593f5a66df9bf262a60ee814304593a6719ae5de43" } } ], "extra": [ 1, 32, 166, 190, 127, 211, 85, 57, 215, 245, 56, 154, 184, 198, 225, 27, 155, 175, 144, 59, 14, 204, 103, 76, 209, 150, 29, 152, 55, 160, 100, 197, 18, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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