Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d81b7f32007e7d32dea75b237cb3b640de7a4c224fc528434b3448b60da0246f

Tx prefix hash: b4e1369e8356223c3795f2f76b29a211ee35bc3a9da655980fb793bef7b7b321
Tx public key: 05dff897559473c3bf2fce77d66d11b1d7e8140617a5032e1787a29100ef464e
Timestamp: 1725582894 Timestamp [UCT]: 2024-09-06 00:34:54 Age [y:d:h:m:s]: 00:261:18:36:10
Block: 1103847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186969 RingCT/type: yes/0
Extra: 0105dff897559473c3bf2fce77d66d11b1d7e8140617a5032e1787a29100ef464e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e5a9a4a8249d10aaa991fb7b54814ca708eae7fcfc2aa335e25b912d0a4b14 0.600000000000 1580832 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": 1103857, "vin": [ { "gen": { "height": 1103847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e5a9a4a8249d10aaa991fb7b54814ca708eae7fcfc2aa335e25b912d0a4b14" } } ], "extra": [ 1, 5, 223, 248, 151, 85, 148, 115, 195, 191, 47, 206, 119, 214, 109, 17, 177, 215, 232, 20, 6, 23, 165, 3, 46, 23, 135, 162, 145, 0, 239, 70, 78, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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