Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e9246dbe6fa5f4f080d889a38fd07727438ee1fec850a5fdf6f37e975d5ef0c

Tx prefix hash: 60794e744bca340ec9a78b015fb4f6342615d4d2f17d476d3eb807bb1798d2f5
Tx public key: 1af901efc1df2f9c8b1f9127ca621dc1a610de317ce2693a97ff9d543f5afdda
Timestamp: 1699303228 Timestamp [UCT]: 2023-11-06 20:40:28 Age [y:d:h:m:s]: 01:223:11:03:04
Block: 885970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420834 RingCT/type: yes/0
Extra: 011af901efc1df2f9c8b1f9127ca621dc1a610de317ce2693a97ff9d543f5afdda02110000000b33af99f4000000000000000000

1 output(s) for total of 0.711891177000 dcy

stealth address amount amount idx
00: a91080c81c292d4b856cfeace38d8f9a8651a6a0c1c208b0470c04b6bece431b 0.711891177000 1341771 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": 885980, "vin": [ { "gen": { "height": 885970 } } ], "vout": [ { "amount": 711891177, "target": { "key": "a91080c81c292d4b856cfeace38d8f9a8651a6a0c1c208b0470c04b6bece431b" } } ], "extra": [ 1, 26, 249, 1, 239, 193, 223, 47, 156, 139, 31, 145, 39, 202, 98, 29, 193, 166, 16, 222, 49, 124, 226, 105, 58, 151, 255, 157, 84, 63, 90, 253, 218, 2, 17, 0, 0, 0, 11, 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