Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b5c00b5b0443fad03b28dadc91b08a02fc67d5380841ec0fa555bcea2c2227

Tx prefix hash: cb762ca0c24fced380aa363f7e03eb92c72a7e920f5ec290ec55c3cab9b8b347
Tx public key: 6a2bddf0c002c1a9d703f8e036183d1f221090d5782b5bcafce8413d88434657
Timestamp: 1735377955 Timestamp [UCT]: 2024-12-28 09:25:55 Age [y:d:h:m:s]: 00:110:09:52:04
Block: 1184914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78701 RingCT/type: yes/0
Extra: 016a2bddf0c002c1a9d703f8e036183d1f221090d5782b5bcafce8413d88434657021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a972be6ce31676251d55dc405fcc2f33b9c19d7a0d233160b8b506a6a565714 0.600000000000 1671377 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": 1184924, "vin": [ { "gen": { "height": 1184914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a972be6ce31676251d55dc405fcc2f33b9c19d7a0d233160b8b506a6a565714" } } ], "extra": [ 1, 106, 43, 221, 240, 192, 2, 193, 169, 215, 3, 248, 224, 54, 24, 61, 31, 34, 16, 144, 213, 120, 43, 91, 202, 252, 232, 65, 61, 136, 67, 70, 87, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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