Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c53e1b865f81a01acf4c356f0baa8ce2a1ce0d983ff561161a05f397fdaf5989

Tx prefix hash: 8263d448a14981b7a7d2fb8c988848e34af48b7ef423d6d986df94d85cd90bb1
Tx public key: 59437f5a5e7d092db1af21afbd409fc6d53443ef2fb3e80d40fffe44c62126bd
Timestamp: 1727007577 Timestamp [UCT]: 2024-09-22 12:19:37 Age [y:d:h:m:s]: 00:109:15:46:00
Block: 1115657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78400 RingCT/type: yes/0
Extra: 0159437f5a5e7d092db1af21afbd409fc6d53443ef2fb3e80d40fffe44c62126bd02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 983899aa312ab9c0abc1d42eb778781f8b7212acc96efd9271ba4b6634ceb761 0.600000000000 1595866 of 15

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": 1115667, "vin": [ { "gen": { "height": 1115657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "983899aa312ab9c0abc1d42eb778781f8b7212acc96efd9271ba4b6634ceb761" } } ], "extra": [ 1, 89, 67, 127, 90, 94, 125, 9, 45, 177, 175, 33, 175, 189, 64, 159, 198, 213, 52, 67, 239, 47, 179, 232, 13, 64, 255, 254, 68, 198, 33, 38, 189, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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