Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b3613f31df6f5a58f8ea9617e45f65e1234b7761e5193c965454ff73b27ae56

Tx prefix hash: 85742c0b1ada10d9b47e112e0f1e599ea425521add7d0e15118a07245507516e
Tx public key: 56c1a721cccab6289b0042bca13ceec510e96008466800d3f00ab6d908c0df9d
Timestamp: 1662189931 Timestamp [UCT]: 2022-09-03 07:25:31 Age [y:d:h:m:s]: 02:209:22:04:36
Block: 579784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671265 RingCT/type: yes/0
Extra: 0156c1a721cccab6289b0042bca13ceec510e96008466800d3f00ab6d908c0df9d02110000001333af99f4000000000000000000

1 output(s) for total of 7.360969476000 dcy

stealth address amount amount idx
00: 284599412b0996efef8edaebdc0e6d9375c87bafac92d2f6d1e512618e99af50 7.360969476000 1013270 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": 579794, "vin": [ { "gen": { "height": 579784 } } ], "vout": [ { "amount": 7360969476, "target": { "key": "284599412b0996efef8edaebdc0e6d9375c87bafac92d2f6d1e512618e99af50" } } ], "extra": [ 1, 86, 193, 167, 33, 204, 202, 182, 40, 155, 0, 66, 188, 161, 60, 238, 197, 16, 233, 96, 8, 70, 104, 0, 211, 240, 10, 182, 217, 8, 192, 223, 157, 2, 17, 0, 0, 0, 19, 51, 175, 153, 244, 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