Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 621632a7e318356f8f8645dfbdd76c28f4e3dd542863d5cb54fbee984f1be1b4

Tx prefix hash: fb8a39702febcbb53453017609511b9cc15f08051a533af7d1b14e00c49e1b9a
Tx public key: b069ba6c6e4f72111712d2cab4fe861ff00f07749d6bc7440ba9917eddaef54b
Timestamp: 1707358766 Timestamp [UCT]: 2024-02-08 02:19:26 Age [y:d:h:m:s]: 01:043:13:46:18
Block: 952744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292200 RingCT/type: yes/0
Extra: 01b069ba6c6e4f72111712d2cab4fe861ff00f07749d6bc7440ba9917eddaef54b0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89015e5e93e7ae6be80631f84b3cc074da4d408734796eb13f583bdce90215c3 0.600000000000 1411872 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": 952754, "vin": [ { "gen": { "height": 952744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89015e5e93e7ae6be80631f84b3cc074da4d408734796eb13f583bdce90215c3" } } ], "extra": [ 1, 176, 105, 186, 108, 110, 79, 114, 17, 23, 18, 210, 202, 180, 254, 134, 31, 240, 15, 7, 116, 157, 107, 199, 68, 11, 169, 145, 126, 221, 174, 245, 75, 2, 17, 0, 0, 0, 6, 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