Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1040dee9cfa791bf4017e6f5d5ec786ef166bbdf5dfd46157de0299e3a1719b2

Tx prefix hash: 51f27904bbd033487a848986a927949ffd8248bcfe593fa9815c641d88aecb48
Tx public key: 9efc6f6579bf6e8982945cf0955cb4233d2743c83d1c90732b1a33abf6bfa13f
Timestamp: 1741460173 Timestamp [UCT]: 2025-03-08 18:56:13 Age [y:d:h:m:s]: 00:320:07:16:26
Block: 1235016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226602 RingCT/type: yes/0
Extra: 019efc6f6579bf6e8982945cf0955cb4233d2743c83d1c90732b1a33abf6bfa13f0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ef8b6b2e73807393f0f71235e3ba8d66ec82e7f2ca3f13e857f6462f9c418f 0.600000000000 1721951 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": 1235026, "vin": [ { "gen": { "height": 1235016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ef8b6b2e73807393f0f71235e3ba8d66ec82e7f2ca3f13e857f6462f9c418f" } } ], "extra": [ 1, 158, 252, 111, 101, 121, 191, 110, 137, 130, 148, 92, 240, 149, 92, 180, 35, 61, 39, 67, 200, 61, 28, 144, 115, 43, 26, 51, 171, 246, 191, 161, 63, 2, 17, 0, 0, 0, 8, 31, 10, 83, 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