Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf55fc3fabbf2ad5b16730f527ae9ebd4087a9a41095d4d61391bf407cd75501

Tx prefix hash: b90bd250bf41bcbda3fecb46a75c63d3d3743e108bf1ec707b988bfec30121bc
Tx public key: 839d4f5cd964b74727930736b257ee1a24f8019c9518744d24dde3d8b61b1e42
Timestamp: 1772534571 Timestamp [UTC]: 2026-03-03 10:42:51 Age [y:d:h:m:s]: 00:257:00:18:14
Block: 1489724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189120 RingCT/type: yes/0
Extra: 01839d4f5cd964b74727930736b257ee1a24f8019c9518744d24dde3d8b61b1e42021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bdb46defd9572ae71f1678727d73f96981b5c9f2a9675cbafdfd4abc5b33aeec 0.000600000000 1979222 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": 1489734, "vin": [ { "gen": { "height": 1489724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdb46defd9572ae71f1678727d73f96981b5c9f2a9675cbafdfd4abc5b33aeec" } } ], "extra": [ 1, 131, 157, 79, 92, 217, 100, 183, 71, 39, 147, 7, 54, 178, 87, 238, 26, 36, 248, 1, 156, 149, 24, 116, 77, 36, 221, 227, 216, 182, 27, 30, 66, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: