Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e353547f264cb4c25115721eaae8108c71a924f1bb5809230786b8c8770174bd

Tx prefix hash: fc8daa6094c5fb8f4e4dced78c96eef80abd13b6841eb7add81a64e78423861b
Tx public key: 104d2e11e329754f1ec6114a045e158f90bde25f41d0f8df647f42e138f23f4e
Timestamp: 1705616575 Timestamp [UCT]: 2024-01-18 22:22:55 Age [y:d:h:m:s]: 00:358:08:22:52
Block: 938296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256563 RingCT/type: yes/0
Extra: 01104d2e11e329754f1ec6114a045e158f90bde25f41d0f8df647f42e138f23f4e02110000000282025268000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b96bfa66e27504c3d5561445b86b8f8c5a39b756f88ba62478d3242e79153d62 0.600000000000 1396366 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": 938306, "vin": [ { "gen": { "height": 938296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b96bfa66e27504c3d5561445b86b8f8c5a39b756f88ba62478d3242e79153d62" } } ], "extra": [ 1, 16, 77, 46, 17, 227, 41, 117, 79, 30, 198, 17, 74, 4, 94, 21, 143, 144, 189, 226, 95, 65, 208, 248, 223, 100, 127, 66, 225, 56, 242, 63, 78, 2, 17, 0, 0, 0, 2, 130, 2, 82, 104, 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