Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99b49454ad8db9b58f411dc12f02ebc7fa31ae1e4c7add698c8d79528f4bd878

Tx prefix hash: 47ee7c0ab8334478eb96510e4079eca5aee43a3de25c756e7f1ffd05bcbda12c
Tx public key: 5905f74b394fe6c733822fbe8f0e73102f2caac3d3f4f06a7f3232b4485c2a6d
Timestamp: 1725595436 Timestamp [UCT]: 2024-09-06 04:03:56 Age [y:d:h:m:s]: 00:266:00:01:06
Block: 1103943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189998 RingCT/type: yes/0
Extra: 015905f74b394fe6c733822fbe8f0e73102f2caac3d3f4f06a7f3232b4485c2a6d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a13e44b30bc651acb1d48918f2528630ff00406f1bb2a451ee794520a214683 0.600000000000 1580966 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": 1103953, "vin": [ { "gen": { "height": 1103943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a13e44b30bc651acb1d48918f2528630ff00406f1bb2a451ee794520a214683" } } ], "extra": [ 1, 89, 5, 247, 75, 57, 79, 230, 199, 51, 130, 47, 190, 143, 14, 115, 16, 47, 44, 170, 195, 211, 244, 240, 106, 127, 50, 50, 180, 72, 92, 42, 109, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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