Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca3dbb03f57816fc013d8fda8a9c536d1e0e10cd55e4ddf636de9a91fe8c4f7d

Tx prefix hash: 0dc35bf77854af74ac2c783763c5cba2a78e321dad149963d79e12183857a72d
Tx public key: 67b8a33bd979e53c05688617f1e4062c978f0413db5ecf4f5d59489eb8ac3439
Timestamp: 1644429813 Timestamp [UCT]: 2022-02-09 18:03:33 Age [y:d:h:m:s]: 02:281:00:43:32
Block: 435135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720002 RingCT/type: yes/0
Extra: 0167b8a33bd979e53c05688617f1e4062c978f0413db5ecf4f5d59489eb8ac34390211000000064a0f5013000000000000000000

1 output(s) for total of 22.193071504000 dcy

stealth address amount amount idx
00: 13f1649fc81f0cdba0a8a59cbcd72322805def8bc60d4b61e5305b1ebee4b4d9 22.193071504000 846234 of 0

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": 435145, "vin": [ { "gen": { "height": 435135 } } ], "vout": [ { "amount": 22193071504, "target": { "key": "13f1649fc81f0cdba0a8a59cbcd72322805def8bc60d4b61e5305b1ebee4b4d9" } } ], "extra": [ 1, 103, 184, 163, 59, 217, 121, 229, 60, 5, 104, 134, 23, 241, 228, 6, 44, 151, 143, 4, 19, 219, 94, 207, 79, 93, 89, 72, 158, 184, 172, 52, 57, 2, 17, 0, 0, 0, 6, 74, 15, 80, 19, 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