Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49e92bd31c5a0f7897cc7bc51876c4152db56661a7d1cc0f49ed914aef148dd0

Tx prefix hash: 800ed581b28069080d0f4e56b4b369dc8bb808e2dfc0ea86706cd469bbd08ebf
Tx public key: b2c989ccd50cb9d37aff3f453d51ce71c838e043e37e905ae9f459ff4efb9cfe
Timestamp: 1768096258 Timestamp [UTC]: 2026-01-11 01:50:58 Age [y:d:h:m:s]: 00:035:01:52:02
Block: 1453160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 24913 RingCT/type: yes/0
Extra: 01b2c989ccd50cb9d37aff3f453d51ce71c838e043e37e905ae9f459ff4efb9cfe0209000000088970985800

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc9d575d679931125ee0396ede050994ca487182daba266c091a268ec3aae077 0.000600000000 1942206 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": 1453170, "vin": [ { "gen": { "height": 1453160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc9d575d679931125ee0396ede050994ca487182daba266c091a268ec3aae077" } } ], "extra": [ 1, 178, 201, 137, 204, 213, 12, 185, 211, 122, 255, 63, 69, 61, 81, 206, 113, 200, 56, 224, 67, 227, 126, 144, 90, 233, 244, 89, 255, 78, 251, 156, 254, 2, 9, 0, 0, 0, 8, 137, 112, 152, 88, 0 ], "rct_signatures": { "type": 0 } }


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