Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559d6e338e9c363c89a14e2af5f9d2fad31bc14a2e15e0c40a6da2d617b887ba

Tx prefix hash: 444a06d1ee1d926ac5121fa504f7a0a6de5a1f88271c6b80490e9598317fd639
Tx public key: 2a4795590ae52f0ebb112f9e7fe55f42a88c97719e918329fcd94a0fd6bf1523
Timestamp: 1599878682 Timestamp [UCT]: 2020-09-12 02:44:42 Age [y:d:h:m:s]: 04:106:19:45:15
Block: 134264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1049609 RingCT/type: yes/0
Extra: 012a4795590ae52f0ebb112f9e7fe55f42a88c97719e918329fcd94a0fd6bf15230211000000144ac5aa02000000000000000000

1 output(s) for total of 220.357757899000 dcy

stealth address amount amount idx
00: f500b5fd4a141712b62df1837d628de2348b42c0165ff4b5febce34c0901e50d 220.357757899000 223751 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": 134274, "vin": [ { "gen": { "height": 134264 } } ], "vout": [ { "amount": 220357757899, "target": { "key": "f500b5fd4a141712b62df1837d628de2348b42c0165ff4b5febce34c0901e50d" } } ], "extra": [ 1, 42, 71, 149, 89, 10, 229, 47, 14, 187, 17, 47, 158, 127, 229, 95, 66, 168, 140, 151, 113, 158, 145, 131, 41, 252, 217, 74, 15, 214, 191, 21, 35, 2, 17, 0, 0, 0, 20, 74, 197, 170, 2, 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