Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdaa47d589323ccbd2ad61de538965aa35b528cba6591ef65178dbdcdea83987

Tx prefix hash: 10ce0b3ea5cf6d03ae1801635459d482abe455d25a57c6a40220c2e0449db06e
Tx public key: 1f7cffb5c4ece1557527af751897987328df332e90eb46157a14e4f6c87e95a6
Timestamp: 1773338885 Timestamp [UTC]: 2026-03-12 18:08:05 Age [y:d:h:m:s]: 00:250:10:35:41
Block: 1496400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184491 RingCT/type: yes/0
Extra: 011f7cffb5c4ece1557527af751897987328df332e90eb46157a14e4f6c87e95a6021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0bf17e4586bd47c459e3db2e273d4d7ae09b3ca1fb136d65ad3aa0545a859cee 0.000600000000 1986024 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": 1496410, "vin": [ { "gen": { "height": 1496400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bf17e4586bd47c459e3db2e273d4d7ae09b3ca1fb136d65ad3aa0545a859cee" } } ], "extra": [ 1, 31, 124, 255, 181, 196, 236, 225, 85, 117, 39, 175, 117, 24, 151, 152, 115, 40, 223, 51, 46, 144, 235, 70, 21, 122, 20, 228, 246, 200, 126, 149, 166, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: