Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4278e746af17e21cd21a52f0f692d3040ab76dede9b1b1b87ff39a14e7a62b19

Tx prefix hash: 649c54ad24f53cbae6ce19d22954853fe3fba797fb353ea376f5bdea0caa47bd
Tx public key: 676763f11630e2e8a17dc0cd5d1603019cb0fc9b496eaa39688b47b3ac344ef3
Timestamp: 1724435297 Timestamp [UCT]: 2024-08-23 17:48:17 Age [y:d:h:m:s]: 00:231:05:06:09
Block: 1094335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165113 RingCT/type: yes/0
Extra: 01676763f11630e2e8a17dc0cd5d1603019cb0fc9b496eaa39688b47b3ac344ef3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43b3cdf3e02189a0797c523a0c7eff60131dd9d69b8da964a962cf991abe2984 0.600000000000 1569452 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": 1094345, "vin": [ { "gen": { "height": 1094335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43b3cdf3e02189a0797c523a0c7eff60131dd9d69b8da964a962cf991abe2984" } } ], "extra": [ 1, 103, 103, 99, 241, 22, 48, 226, 232, 161, 125, 192, 205, 93, 22, 3, 1, 156, 176, 252, 155, 73, 110, 170, 57, 104, 139, 71, 179, 172, 52, 78, 243, 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