Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c52d983892e83b8a4e40694a594bb9b89fa32923fe6d0758f8dd07d6abb51f5

Tx prefix hash: da01d6c50078ee523be6d3d258c5608113a44754aaadd10c6a1394408c20c268
Tx public key: 36a1a21a2f41ff1277eebef9a7551985c6ff0e9a32c4b8332bef79c1ee46d989
Timestamp: 1724764062 Timestamp [UCT]: 2024-08-27 13:07:42 Age [y:d:h:m:s]: 00:223:12:30:18
Block: 1097051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159592 RingCT/type: yes/0
Extra: 0136a1a21a2f41ff1277eebef9a7551985c6ff0e9a32c4b8332bef79c1ee46d989021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 481feb09aec7f44e4a75f3da9f7ac9ab81557dcd7f53a771ffdeb63f3044c8a1 0.600000000000 1572330 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": 1097061, "vin": [ { "gen": { "height": 1097051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "481feb09aec7f44e4a75f3da9f7ac9ab81557dcd7f53a771ffdeb63f3044c8a1" } } ], "extra": [ 1, 54, 161, 162, 26, 47, 65, 255, 18, 119, 238, 190, 249, 167, 85, 25, 133, 198, 255, 14, 154, 50, 196, 184, 51, 43, 239, 121, 193, 238, 70, 217, 137, 2, 17, 0, 0, 0, 7, 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