Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e0378b8a7ba47cbf23542ece9f0214f983b8a8eb102fc403ff396d9fd09f981

Tx prefix hash: 176a571b79b6ef0042dc836d22f9cc3b9ad47924e99cd332fcb6fd6251919967
Tx public key: 65a92d0f6d7f00a1e2512224aef5fcbdb4ff76ee62e939b5b2662b8b5a592bf3
Timestamp: 1706867306 Timestamp [UCT]: 2024-02-02 09:48:26 Age [y:d:h:m:s]: 01:027:10:23:07
Block: 948674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280638 RingCT/type: yes/0
Extra: 0165a92d0f6d7f00a1e2512224aef5fcbdb4ff76ee62e939b5b2662b8b5a592bf30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b927db4652f63df603205a695de18be3a1eaed1ff29ff99bbf1b03d44497f86e 0.600000000000 1407128 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": 948684, "vin": [ { "gen": { "height": 948674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b927db4652f63df603205a695de18be3a1eaed1ff29ff99bbf1b03d44497f86e" } } ], "extra": [ 1, 101, 169, 45, 15, 109, 127, 0, 161, 226, 81, 34, 36, 174, 245, 252, 189, 180, 255, 118, 238, 98, 233, 57, 181, 178, 102, 43, 139, 90, 89, 43, 243, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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