Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a95ec58f078e4d06d0a078d743e498876fee4abf33ef9cf9aae69171e2f84753

Tx prefix hash: c40456abfb3da24857b23ee85da58db6cb069d59a5b91dab031f161009344c04
Tx public key: af40181f7aa66f9822e5eab917f782b00b6fbb91212c6a96febe6c43736a16d4
Timestamp: 1581242336 Timestamp [UCT]: 2020-02-09 09:58:56 Age [y:d:h:m:s]: 05:024:21:36:25
Block: 61186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170619 RingCT/type: yes/0
Extra: 01af40181f7aa66f9822e5eab917f782b00b6fbb91212c6a96febe6c43736a16d40211000000410aca7173000000000000000000

1 output(s) for total of 384.871068310000 dcy

stealth address amount amount idx
00: faefc7c04b9922300b2f2f4f7a904c0a66fad2f2270605cdd8a044d4c34638b9 384.871068310000 112754 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": 61196, "vin": [ { "gen": { "height": 61186 } } ], "vout": [ { "amount": 384871068310, "target": { "key": "faefc7c04b9922300b2f2f4f7a904c0a66fad2f2270605cdd8a044d4c34638b9" } } ], "extra": [ 1, 175, 64, 24, 31, 122, 166, 111, 152, 34, 229, 234, 185, 23, 247, 130, 176, 11, 111, 187, 145, 33, 44, 106, 150, 254, 190, 108, 67, 115, 106, 22, 212, 2, 17, 0, 0, 0, 65, 10, 202, 113, 115, 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