Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4cdbf5765c9c785e73fa9f616565a27f88b2dfe6dc47b9b3ecf8da375133d0

Tx prefix hash: f4fceb08f3fa92f214e871cc765eb7bcd7e38fadcca3411710b814b46aad8b14
Tx public key: de560a475cad4e99c6d7aeadbefe655b39535d6d512856b2b12934f96af27a40
Timestamp: 1718387731 Timestamp [UCT]: 2024-06-14 17:55:31 Age [y:d:h:m:s]: 01:009:03:29:01
Block: 1044196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267165 RingCT/type: yes/0
Extra: 01de560a475cad4e99c6d7aeadbefe655b39535d6d512856b2b12934f96af27a400211000000038fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58620ca7fd19cfaf8dbdae1cefef9c0ddc32ec9a0d3da1cad45dd4ed70f05320 0.600000000000 1513439 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": 1044206, "vin": [ { "gen": { "height": 1044196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58620ca7fd19cfaf8dbdae1cefef9c0ddc32ec9a0d3da1cad45dd4ed70f05320" } } ], "extra": [ 1, 222, 86, 10, 71, 92, 173, 78, 153, 198, 215, 174, 173, 190, 254, 101, 91, 57, 83, 93, 109, 81, 40, 86, 178, 177, 41, 52, 249, 106, 242, 122, 64, 2, 17, 0, 0, 0, 3, 143, 218, 155, 45, 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