Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0bddf5aeb9611437c2837ba6a4dd00352b3bb7ffae514766007e4d7dbf73d48

Tx prefix hash: 876272842003f7d71b897d52c735369a77a60d9075f5de2dc93fcce6ba6c618e
Tx public key: 417ca044140e603e8fc43ab29a324cc1b0d9aa7af3729ea8fba77dd65f2585b3
Timestamp: 1632295643 Timestamp [UCT]: 2021-09-22 07:27:23 Age [y:d:h:m:s]: 03:107:14:48:23
Block: 338642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 853094 RingCT/type: yes/0
Extra: 01417ca044140e603e8fc43ab29a324cc1b0d9aa7af3729ea8fba77dd65f2585b302110000000137cb3088000000000000000000

1 output(s) for total of 46.338173483000 dcy

stealth address amount amount idx
00: 83468559316452cfdb20e866f39336e3e9d5f6edb8d41c709fbf3a6c1551828e 46.338173483000 696859 of 0

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": 338652, "vin": [ { "gen": { "height": 338642 } } ], "vout": [ { "amount": 46338173483, "target": { "key": "83468559316452cfdb20e866f39336e3e9d5f6edb8d41c709fbf3a6c1551828e" } } ], "extra": [ 1, 65, 124, 160, 68, 20, 14, 96, 62, 143, 196, 58, 178, 154, 50, 76, 193, 176, 217, 170, 122, 243, 114, 158, 168, 251, 167, 125, 214, 95, 37, 133, 179, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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