Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33fa4f9c063803ec4ad4c8bd4b5012b4183791c3db7c90eaba873dcbfd7893d9

Tx prefix hash: 7f4512719c1705a6813793b6a8a3a7b0cf5d16a184da0a1ffadaae41f5aec3fd
Tx public key: ea303a8e6b0d4ddc1743c44e41ad95892d7d6e1751b91b94d8a65e60e19401df
Timestamp: 1716993942 Timestamp [UCT]: 2024-05-29 14:45:42 Age [y:d:h:m:s]: 00:303:10:58:31
Block: 1032636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216874 RingCT/type: yes/0
Extra: 01ea303a8e6b0d4ddc1743c44e41ad95892d7d6e1751b91b94d8a65e60e19401df02110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b340aea914cb8b806e68e1086364dd727110acf496a4880cfd4294b36964643 0.600000000000 1501089 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": 1032646, "vin": [ { "gen": { "height": 1032636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b340aea914cb8b806e68e1086364dd727110acf496a4880cfd4294b36964643" } } ], "extra": [ 1, 234, 48, 58, 142, 107, 13, 77, 220, 23, 67, 196, 78, 65, 173, 149, 137, 45, 125, 110, 23, 81, 185, 27, 148, 216, 166, 94, 96, 225, 148, 1, 223, 2, 17, 0, 0, 0, 15, 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