Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b05f1334f20534ad513281e9f6e7e6a56a7b9f21475998dc7d51551d31def0cf

Tx prefix hash: 2f8d2b45210a6097d8090b8a2a6a1c91d223702d26d7ecd09abc2015dce49534
Tx public key: cdfc60ce6f5983b60e38f4f94c79ed734501a0cff5059cd0be9da700f246ae8a
Timestamp: 1582020663 Timestamp [UCT]: 2020-02-18 10:11:03 Age [y:d:h:m:s]: 04:274:08:58:19
Block: 67323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1088555 RingCT/type: yes/0
Extra: 01cdfc60ce6f5983b60e38f4f94c79ed734501a0cff5059cd0be9da700f246ae8a0211000000064ac5aa02000000000000000000

1 output(s) for total of 367.224595813000 dcy

stealth address amount amount idx
00: 80f2f24018deafabf762c4ce02025a3e0c6a4fc5e12c0f7a3513541b96ef0243 367.224595813000 124077 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": 67333, "vin": [ { "gen": { "height": 67323 } } ], "vout": [ { "amount": 367224595813, "target": { "key": "80f2f24018deafabf762c4ce02025a3e0c6a4fc5e12c0f7a3513541b96ef0243" } } ], "extra": [ 1, 205, 252, 96, 206, 111, 89, 131, 182, 14, 56, 244, 249, 76, 121, 237, 115, 69, 1, 160, 207, 245, 5, 156, 208, 190, 157, 167, 0, 242, 70, 174, 138, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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