Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfbba8679b8ed36522eea1f2705a181ee960a63ec13287dbdcc8dd13ac0ba57d

Tx prefix hash: 414fade7259d294537e2a21a3c945bad439259db1e9da8d2921dde95f616d4d7
Tx public key: 6aab9399689a62fdb81d5bc6c0b620aefcdec48a68ec3b0128825c087b3300fd
Timestamp: 1648499681 Timestamp [UCT]: 2022-03-28 20:34:41 Age [y:d:h:m:s]: 03:030:18:31:28
Block: 468441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 802220 RingCT/type: yes/0
Extra: 016aab9399689a62fdb81d5bc6c0b620aefcdec48a68ec3b0128825c087b3300fd02110000000506faf294000000000000000000

1 output(s) for total of 17.213166104000 dcy

stealth address amount amount idx
00: 40dede8a05d76c49751ecc5d2b5afe0167953f2c2bc54a568d63b29f905fdf3b 17.213166104000 887161 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": 468451, "vin": [ { "gen": { "height": 468441 } } ], "vout": [ { "amount": 17213166104, "target": { "key": "40dede8a05d76c49751ecc5d2b5afe0167953f2c2bc54a568d63b29f905fdf3b" } } ], "extra": [ 1, 106, 171, 147, 153, 104, 154, 98, 253, 184, 29, 91, 198, 192, 182, 32, 174, 252, 222, 196, 138, 104, 236, 59, 1, 40, 130, 92, 8, 123, 51, 0, 253, 2, 17, 0, 0, 0, 5, 6, 250, 242, 148, 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