Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ade3b541d3fefd4c1c23c8c4d396d5603a19e725e18a5fa572b774876e7116d

Tx prefix hash: 800e61eb8861af08294f95f88a5d003df637b8ffcaf27512f187b262fbfd82f2
Tx public key: f93f5b55dd35e80d386b2fa9088d772eead7903325d01096cb4ae265a1ad9214
Timestamp: 1706291073 Timestamp [UCT]: 2024-01-26 17:44:33 Age [y:d:h:m:s]: 01:288:20:19:57
Block: 943870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465256 RingCT/type: yes/0
Extra: 01f93f5b55dd35e80d386b2fa9088d772eead7903325d01096cb4ae265a1ad92140211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dc75e2cf3f01293a1310916f22e95e9b869a56f6c4edb7e80f5f9339d16efd6 0.600000000000 1402096 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": 943880, "vin": [ { "gen": { "height": 943870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dc75e2cf3f01293a1310916f22e95e9b869a56f6c4edb7e80f5f9339d16efd6" } } ], "extra": [ 1, 249, 63, 91, 85, 221, 53, 232, 13, 56, 107, 47, 169, 8, 141, 119, 46, 234, 215, 144, 51, 37, 208, 16, 150, 203, 74, 226, 101, 161, 173, 146, 20, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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