Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10e8f2690fc8731bf07e0a5d7e9911f2fbc7fb20bab261d782c2e769fd726fc3

Tx prefix hash: b5f2318e7285602ddd0e95257fb31e96895f75d124725572da5b5021f4929a69
Tx public key: e3b5ad540a341ae0d52a03ccd60121180ce048244754d832a52c23ea9158416f
Timestamp: 1715718685 Timestamp [UCT]: 2024-05-14 20:31:25 Age [y:d:h:m:s]: 00:051:22:24:35
Block: 1022057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37196 RingCT/type: yes/0
Extra: 01e3b5ad540a341ae0d52a03ccd60121180ce048244754d832a52c23ea9158416f021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74a7fd5edae48a5f661edbaf44f81da49f461479273904a4c58bbd2f95708a47 0.600000000000 1486550 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": 1022067, "vin": [ { "gen": { "height": 1022057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74a7fd5edae48a5f661edbaf44f81da49f461479273904a4c58bbd2f95708a47" } } ], "extra": [ 1, 227, 181, 173, 84, 10, 52, 26, 224, 213, 42, 3, 204, 214, 1, 33, 24, 12, 224, 72, 36, 71, 84, 216, 50, 165, 44, 35, 234, 145, 88, 65, 111, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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