Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 833d295280f2d7c77132e3e74c654e3838df32ddad8625624f3c55366e9aee1b

Tx prefix hash: 6910df87e1d760918726ef9cdd59dcdf337e38c1878bc93d190deafa1bab2272
Tx public key: 0ec5b983e34808e33ce2c59dbab6a5ef655edf9a4aea837f265051f556f8a813
Timestamp: 1724967387 Timestamp [UCT]: 2024-08-29 21:36:27 Age [y:d:h:m:s]: 01:040:01:54:14
Block: 1098734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287038 RingCT/type: yes/0
Extra: 010ec5b983e34808e33ce2c59dbab6a5ef655edf9a4aea837f265051f556f8a813021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd97f20389d6720f4f78a9ad25fe7a1610dfc2e6b6a1d6103bc12a06ad046d18 0.600000000000 1574553 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": 1098744, "vin": [ { "gen": { "height": 1098734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd97f20389d6720f4f78a9ad25fe7a1610dfc2e6b6a1d6103bc12a06ad046d18" } } ], "extra": [ 1, 14, 197, 185, 131, 227, 72, 8, 227, 60, 226, 197, 157, 186, 182, 165, 239, 101, 94, 223, 154, 74, 234, 131, 127, 38, 80, 81, 245, 86, 248, 168, 19, 2, 17, 0, 0, 0, 2, 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