Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0434721e90092be87dcf56d049d0de10bc6e04dfebf83557e76e68bad9e6550e

Tx prefix hash: abe27baa923fc98d0a0861a7a20c4c6153a1014225b15226ccd8dfabcaa60dc6
Tx public key: a57d1bae5d27bbf6f614856a952a8e202a9b6fd7e888a704d8529071af62f261
Timestamp: 1719965666 Timestamp [UCT]: 2024-07-03 00:14:26 Age [y:d:h:m:s]: 00:302:01:37:02
Block: 1057257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215853 RingCT/type: yes/0
Extra: 01a57d1bae5d27bbf6f614856a952a8e202a9b6fd7e888a704d8529071af62f2610211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2e00307f8fbfe73f3fc18e53e755e50c863336ffb1ad23edcbb85d55959aad 0.600000000000 1527690 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": 1057267, "vin": [ { "gen": { "height": 1057257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2e00307f8fbfe73f3fc18e53e755e50c863336ffb1ad23edcbb85d55959aad" } } ], "extra": [ 1, 165, 125, 27, 174, 93, 39, 187, 246, 246, 20, 133, 106, 149, 42, 142, 32, 42, 155, 111, 215, 232, 136, 167, 4, 216, 82, 144, 113, 175, 98, 242, 97, 2, 17, 0, 0, 0, 2, 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