Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d57a9bcb4ca4683383b691e34dfd8914090b49648094af99da78da9c6e9a233

Tx prefix hash: a9c4148eef7cd61dabede63ebcf2c7e54f8a3cdf3df8864ac4dad6d5ae23f35b
Tx public key: 888f299aaac8c37e7b6b3383ae3cafea64a31abf8e41c418c5817cb4947e8c01
Timestamp: 1706480198 Timestamp [UCT]: 2024-01-28 22:16:38 Age [y:d:h:m:s]: 01:070:03:31:52
Block: 945448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311201 RingCT/type: yes/0
Extra: 01888f299aaac8c37e7b6b3383ae3cafea64a31abf8e41c418c5817cb4947e8c010211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f75f3233c756abe0c951d45cb09b4a03f7ae9bb3eb5c66b0c5e3b4f6e74787a7 0.600000000000 1403762 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": 945458, "vin": [ { "gen": { "height": 945448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f75f3233c756abe0c951d45cb09b4a03f7ae9bb3eb5c66b0c5e3b4f6e74787a7" } } ], "extra": [ 1, 136, 143, 41, 154, 170, 200, 195, 126, 123, 107, 51, 131, 174, 60, 175, 234, 100, 163, 26, 191, 142, 65, 196, 24, 197, 129, 124, 180, 148, 126, 140, 1, 2, 17, 0, 0, 0, 5, 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