Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e5567338ee00f93bdd6a0a21ac2693090fe20ff88de2fc4a03a59efdaf598b5

Tx prefix hash: e2c6b83c0e02baafce14d057a8b649a81e8c16e11dd6d4481d4ffdc99b1f4c96
Tx public key: a71e9f792ee0964e81a23f80ac6be4f92838d5d415afdfa064070fd2ed37654f
Timestamp: 1711624982 Timestamp [UCT]: 2024-03-28 11:23:02 Age [y:d:h:m:s]: 01:230:18:47:10
Block: 988135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423621 RingCT/type: yes/0
Extra: 01a71e9f792ee0964e81a23f80ac6be4f92838d5d415afdfa064070fd2ed37654f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7878f13386fd85462df10184bfbacde7640aaee4e0ea6942f460b83a86480fe 0.600000000000 1448402 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": 988145, "vin": [ { "gen": { "height": 988135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7878f13386fd85462df10184bfbacde7640aaee4e0ea6942f460b83a86480fe" } } ], "extra": [ 1, 167, 30, 159, 121, 46, 224, 150, 78, 129, 162, 63, 128, 172, 107, 228, 249, 40, 56, 213, 212, 21, 175, 223, 160, 100, 7, 15, 210, 237, 55, 101, 79, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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