Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d9652387bcd2055bf052dd0296242506c119429947ed5f4e10da67ff3231b9

Tx prefix hash: e4c686cb0e9a6a63d2be38a5cf595742df711cc808fdc362aa4d00378ff73d66
Tx public key: 571aad31a938d2c24f96ef1cc7f99b859c7b32c8971c3843722d690c3ae8d501
Timestamp: 1672649057 Timestamp [UCT]: 2023-01-02 08:44:17 Age [y:d:h:m:s]: 02:152:22:53:45
Block: 665853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631058 RingCT/type: yes/0
Extra: 01571aad31a938d2c24f96ef1cc7f99b859c7b32c8971c3843722d690c3ae8d50102110000000252542ceb000000000000000000

1 output(s) for total of 3.817267243000 dcy

stealth address amount amount idx
00: 35e5d206dd472839a1c6cbefab9f87ef1a2021566b0100ce53c285e2c6057e8b 3.817267243000 1106922 of 0

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": 665863, "vin": [ { "gen": { "height": 665853 } } ], "vout": [ { "amount": 3817267243, "target": { "key": "35e5d206dd472839a1c6cbefab9f87ef1a2021566b0100ce53c285e2c6057e8b" } } ], "extra": [ 1, 87, 26, 173, 49, 169, 56, 210, 194, 79, 150, 239, 28, 199, 249, 155, 133, 156, 123, 50, 200, 151, 28, 56, 67, 114, 45, 105, 12, 58, 232, 213, 1, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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