Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0358043f7edbe7e61d7b8b8c342b72e797d797ab04eff7cb4404c5e255f452dd

Tx prefix hash: fc224080b319f17761b3f6cf7440d318b097b5158259f26479db09131964ebd4
Tx public key: 148a4ae386fa1fdfa5acb19d6ce3a20521f66311d849954273ff6df74de02e38
Timestamp: 1728410428 Timestamp [UCT]: 2024-10-08 18:00:28 Age [y:d:h:m:s]: 01:031:05:32:04
Block: 1127285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280690 RingCT/type: yes/0
Extra: 01148a4ae386fa1fdfa5acb19d6ce3a20521f66311d849954273ff6df74de02e38021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f6fa41a8eaf5be2ae6b6041291c6617a4df1f0f2dfea32581803923482d5bd7 0.600000000000 1610086 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": 1127295, "vin": [ { "gen": { "height": 1127285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f6fa41a8eaf5be2ae6b6041291c6617a4df1f0f2dfea32581803923482d5bd7" } } ], "extra": [ 1, 20, 138, 74, 227, 134, 250, 31, 223, 165, 172, 177, 157, 108, 227, 162, 5, 33, 246, 99, 17, 216, 73, 149, 66, 115, 255, 109, 247, 77, 224, 46, 56, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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