Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c195a1ddc83e634f8dca31037262da9ea414901f2165659f6eb1ba0d40905712

Tx prefix hash: ba401f162af759bc410c06360869a5739f51c71004527fa49fe7a88587f3dc6f
Tx public key: e3342e859275f6f99a6d9dcd49103b3b72f29e38d503bf0c357b2a00f3f4cea7
Timestamp: 1738239044 Timestamp [UCT]: 2025-01-30 12:10:44 Age [y:d:h:m:s]: 00:139:06:33:06
Block: 1208341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99486 RingCT/type: yes/0
Extra: 01e3342e859275f6f99a6d9dcd49103b3b72f29e38d503bf0c357b2a00f3f4cea70211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b490876e6144d8e3420323b8501c846ab111c41d8b73ad0c964e356af64a3a 0.600000000000 1695072 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": 1208351, "vin": [ { "gen": { "height": 1208341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b490876e6144d8e3420323b8501c846ab111c41d8b73ad0c964e356af64a3a" } } ], "extra": [ 1, 227, 52, 46, 133, 146, 117, 246, 249, 154, 109, 157, 205, 73, 16, 59, 59, 114, 242, 158, 56, 213, 3, 191, 12, 53, 123, 42, 0, 243, 244, 206, 167, 2, 17, 0, 0, 0, 7, 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