Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb39d77de7e31cf90d4e6b50881a29a0f44151920daa6ddcc958ea18690be443

Tx prefix hash: 76b4f023c37c5b1b0693d3cdf37bd932e57cd21d1df4d54a7490ce7591c5abce
Tx public key: fed695f7bf561ff3aa49713aaa8c9d9097d0054a0238c89aa67d74aaa2caae74
Timestamp: 1715874647 Timestamp [UCT]: 2024-05-16 15:50:47 Age [y:d:h:m:s]: 00:239:14:40:19
Block: 1023353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171502 RingCT/type: yes/0
Extra: 01fed695f7bf561ff3aa49713aaa8c9d9097d0054a0238c89aa67d74aaa2caae740211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f57b8160d0b88f2888f01ca8a1d90a1b623a4ff4c8a5128023e12e8687182b77 0.600000000000 1488270 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": 1023363, "vin": [ { "gen": { "height": 1023353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f57b8160d0b88f2888f01ca8a1d90a1b623a4ff4c8a5128023e12e8687182b77" } } ], "extra": [ 1, 254, 214, 149, 247, 191, 86, 31, 243, 170, 73, 113, 58, 170, 140, 157, 144, 151, 208, 5, 74, 2, 56, 200, 154, 166, 125, 116, 170, 162, 202, 174, 116, 2, 17, 0, 0, 0, 1, 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