Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d886a6c5aadc8c3faad9dff9dd65903db7abe840edb42eb0f0294c976d8ef156

Tx prefix hash: 881259bea62b4c2ab5493f707498172bdf94609d09c0b6d19cf0a8bbbf71a879
Tx public key: 731d557ba6185d1b66b0bb1ea11a0b2ff42e77ea023d042fa904a6cd982d0ce5
Timestamp: 1713119626 Timestamp [UCT]: 2024-04-14 18:33:46 Age [y:d:h:m:s]: 01:033:10:47:51
Block: 1000497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284894 RingCT/type: yes/0
Extra: 01731d557ba6185d1b66b0bb1ea11a0b2ff42e77ea023d042fa904a6cd982d0ce502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f00382c3c6ce7793fe561a939ab82e7ae0fa586df05fcf3be85393456fec28b 0.600000000000 1460995 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": 1000507, "vin": [ { "gen": { "height": 1000497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f00382c3c6ce7793fe561a939ab82e7ae0fa586df05fcf3be85393456fec28b" } } ], "extra": [ 1, 115, 29, 85, 123, 166, 24, 93, 27, 102, 176, 187, 30, 161, 26, 11, 47, 244, 46, 119, 234, 2, 61, 4, 47, 169, 4, 166, 205, 152, 45, 12, 229, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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