Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48863d0e8583a7e053fa828c33b2e193889b5f291de9b5362c328426b1410c0

Tx prefix hash: 24123b5abff419f6d9376696bc35359e96bab96a2d3c66bdd7525b31d2b5f9a3
Tx public key: 2cfb860cc9022173f79b52b8eb74e0646b9509683d60203d56c7823be215b6e8
Timestamp: 1719925838 Timestamp [UCT]: 2024-07-02 13:10:38 Age [y:d:h:m:s]: 00:232:22:51:29
Block: 1056939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166403 RingCT/type: yes/0
Extra: 012cfb860cc9022173f79b52b8eb74e0646b9509683d60203d56c7823be215b6e80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02d499a303ba2bee9654d9c7402a09786b270f08d8b4c89a0a1f02bbae7d80c1 0.600000000000 1527368 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": 1056949, "vin": [ { "gen": { "height": 1056939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02d499a303ba2bee9654d9c7402a09786b270f08d8b4c89a0a1f02bbae7d80c1" } } ], "extra": [ 1, 44, 251, 134, 12, 201, 2, 33, 115, 247, 155, 82, 184, 235, 116, 224, 100, 107, 149, 9, 104, 61, 96, 32, 61, 86, 199, 130, 59, 226, 21, 182, 232, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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