Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2633b172709a2d70648f87cc6f3a18c769a1d5e6c9df67622ea81f31624903c3

Tx prefix hash: 9f1ea881ed28bc493302d85dcec3de35b4b6df0a27dccdb0467b4ecab1b03d00
Tx public key: 240f151a2a11f877af278c07df4b4e560261c9095849cd0515343f7ee058593b
Timestamp: 1706793104 Timestamp [UCT]: 2024-02-01 13:11:44 Age [y:d:h:m:s]: 01:084:06:40:42
Block: 948046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321325 RingCT/type: yes/0
Extra: 01240f151a2a11f877af278c07df4b4e560261c9095849cd0515343f7ee058593b02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b95623f921eb2fea60e9f96ef689d17633d8ae5bdf4ca8269a92d37e3c4b774e 0.600000000000 1406418 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": 948056, "vin": [ { "gen": { "height": 948046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b95623f921eb2fea60e9f96ef689d17633d8ae5bdf4ca8269a92d37e3c4b774e" } } ], "extra": [ 1, 36, 15, 21, 26, 42, 17, 248, 119, 175, 39, 140, 7, 223, 75, 78, 86, 2, 97, 201, 9, 88, 73, 205, 5, 21, 52, 63, 126, 224, 88, 89, 59, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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