Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b740586a8a3d92c1c06e9f04a74ff02f321f1c0987865b700cf2b34d9fd6bc40

Tx prefix hash: 403ad7954ab882070d1f3ddbadd11193be923fc8bae498b714c07926da1fc581
Tx public key: f52f4de5a7d890d6838efda1f78bb2f7f3f706eb17221e4c8da9be43eff2ce9a
Timestamp: 1738984914 Timestamp [UTC]: 2025-02-08 03:21:54 Age [y:d:h:m:s]: 01:282:20:47:02
Block: 1214516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466227 RingCT/type: yes/0
Extra: 01f52f4de5a7d890d6838efda1f78bb2f7f3f706eb17221e4c8da9be43eff2ce9a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f989c95e1936a358e0a1245766d986a9c6e06f8a1a23f3dab7b82bf2c7c63d80 0.000600000000 1701307 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 dinastycoin-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": 1214526, "vin": [ { "gen": { "height": 1214516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f989c95e1936a358e0a1245766d986a9c6e06f8a1a23f3dab7b82bf2c7c63d80" } } ], "extra": [ 1, 245, 47, 77, 229, 167, 216, 144, 214, 131, 142, 253, 161, 247, 139, 178, 247, 243, 247, 6, 235, 23, 34, 30, 76, 141, 169, 190, 67, 239, 242, 206, 154, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: