Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a409b14f14f0441d00c02a8362797aa617fd2bcf1b7d6e18e442147368d98bbc

Tx prefix hash: 0bba4f122f74c0fc2c01ae782f0bae40550eceffb3a2f7176b7659c358739d81
Tx public key: 7b35e3be17c41e44d1301fe8693ecf17c284850ea7ebe086590ac4a0c548cdf6
Timestamp: 1736546126 Timestamp [UCT]: 2025-01-10 21:55:26 Age [y:d:h:m:s]: 00:159:01:50:23
Block: 1194590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113385 RingCT/type: yes/0
Extra: 017b35e3be17c41e44d1301fe8693ecf17c284850ea7ebe086590ac4a0c548cdf60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 452a73e4f5961fc4c1e2ea5f213c65645e704929e786f9b3c3deded6a337bc4b 0.600000000000 1681167 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": 1194600, "vin": [ { "gen": { "height": 1194590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "452a73e4f5961fc4c1e2ea5f213c65645e704929e786f9b3c3deded6a337bc4b" } } ], "extra": [ 1, 123, 53, 227, 190, 23, 196, 30, 68, 209, 48, 31, 232, 105, 62, 207, 23, 194, 132, 133, 14, 167, 235, 224, 134, 89, 10, 196, 160, 197, 72, 205, 246, 2, 17, 0, 0, 0, 4, 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