Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94cd8106fe0783914a1d2ea621f0be2eb39ec1fdf712dc553bea22696e805ee1

Tx prefix hash: 234ff57e0e46803bf9c9cbb809c0864345462713790c7d148d0cda636f5e9f2d
Tx public key: 21721629e41cea3eecac7814b64b761e0f9bf4ae0f3cf39eaf645b6bd6ee0686
Timestamp: 1705194366 Timestamp [UCT]: 2024-01-14 01:06:06 Age [y:d:h:m:s]: 01:087:20:00:30
Block: 934789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323876 RingCT/type: yes/0
Extra: 0121721629e41cea3eecac7814b64b761e0f9bf4ae0f3cf39eaf645b6bd6ee06860211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f764ec47ceec8307d66c493c4b5fb758a87c053fd2662e8f1db7dda71dff4ddb 0.600000000000 1392805 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": 934799, "vin": [ { "gen": { "height": 934789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f764ec47ceec8307d66c493c4b5fb758a87c053fd2662e8f1db7dda71dff4ddb" } } ], "extra": [ 1, 33, 114, 22, 41, 228, 28, 234, 62, 236, 172, 120, 20, 182, 75, 118, 30, 15, 155, 244, 174, 15, 60, 243, 158, 175, 100, 91, 107, 214, 238, 6, 134, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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