Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b158b26b4d27638e0a46fb1bf6bd55fe1a42b9a308dda995adaa7a2202a3d7cf

Tx prefix hash: 1544f00b9771f22f59ac493f392763e5ed1064a0505b9ae74d0b6aaebb97757e
Tx public key: 79d48b7e285e3ec2af766bfa9717bf8dc5f5ce91b91537368ee31b9a113e0207
Timestamp: 1740215077 Timestamp [UTC]: 2025-02-22 09:04:37 Age [y:d:h:m:s]: 01:266:01:29:12
Block: 1224671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454160 RingCT/type: yes/0
Extra: 0179d48b7e285e3ec2af766bfa9717bf8dc5f5ce91b91537368ee31b9a113e0207021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb0d9547cfae87c77b5144e62b7f2763e371903d221c0a25c8483dcabe1dddae 0.000600000000 1711534 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": 1224681, "vin": [ { "gen": { "height": 1224671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0d9547cfae87c77b5144e62b7f2763e371903d221c0a25c8483dcabe1dddae" } } ], "extra": [ 1, 121, 212, 139, 126, 40, 94, 62, 194, 175, 118, 107, 250, 151, 23, 191, 141, 197, 245, 206, 145, 185, 21, 55, 54, 142, 227, 27, 154, 17, 62, 2, 7, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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: