Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a01b345fa47364f6903b45005d3e0e8e60a15cbbc87a6d619c16d1455ded8f2

Tx prefix hash: 789b56279ed632d9328b86ffa6e29fcea72b0084bb436dba1ec01e7f29e7600e
Tx public key: 815fa67e602f3f0436f434420ead9b9a8a64786ef39a854527ce0dc54d77d5fd
Timestamp: 1702828516 Timestamp [UCT]: 2023-12-17 15:55:16 Age [y:d:h:m:s]: 01:034:01:08:08
Block: 915193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285652 RingCT/type: yes/0
Extra: 01815fa67e602f3f0436f434420ead9b9a8a64786ef39a854527ce0dc54d77d5fd02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05cff57d6d844e05c540a46c870b1f5646fc126f90c2d53987ff1d2d81f8deb4 0.600000000000 1372581 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": 915203, "vin": [ { "gen": { "height": 915193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05cff57d6d844e05c540a46c870b1f5646fc126f90c2d53987ff1d2d81f8deb4" } } ], "extra": [ 1, 129, 95, 166, 126, 96, 47, 63, 4, 54, 244, 52, 66, 14, 173, 155, 154, 138, 100, 120, 110, 243, 154, 133, 69, 39, 206, 13, 197, 77, 119, 213, 253, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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