Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40fff86593a482bcea1b789bb5ea5e936787eb586b54523510b2ba4c43d19ad1

Tx prefix hash: ece0013cfb827bee5904fad9fc8cead8be9343b791a08a1020551d6fb10d07f6
Tx public key: 73f2dc98cb7b678de80efcb6eea4f9e1696088b6724e9362b5586d32c291740d
Timestamp: 1749528871 Timestamp [UCT]: 2025-06-10 04:14:31 Age [y:d:h:m:s]: 00:160:16:05:46
Block: 1301824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112501 RingCT/type: yes/0
Extra: 0173f2dc98cb7b678de80efcb6eea4f9e1696088b6724e9362b5586d32c291740d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83a5b27b094723b2303cdb3329e9fa88bc36ae70e20537a061c7203228e8619b 0.600000000000 1789385 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": 1301834, "vin": [ { "gen": { "height": 1301824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83a5b27b094723b2303cdb3329e9fa88bc36ae70e20537a061c7203228e8619b" } } ], "extra": [ 1, 115, 242, 220, 152, 203, 123, 103, 141, 232, 14, 252, 182, 238, 164, 249, 225, 105, 96, 136, 182, 114, 78, 147, 98, 181, 88, 109, 50, 194, 145, 116, 13, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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