Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5fee2211d5481f648bde97ceb3e1f3bb874314500ec0ba19e0f1eb44b58b94f

Tx prefix hash: b7ed8dbbb56c259df8b961f39179e60617183456ddb1e62de4d63a2ee64b1182
Tx public key: ce4ad568a5506ba812680e9c1cea2fdbb6e8a8343310c27324cd9d1f4ba9cedb
Timestamp: 1768279984 Timestamp [UTC]: 2026-01-13 04:53:04 Age [y:d:h:m:s]: 00:308:13:05:51
Block: 1454539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226005 RingCT/type: yes/0
Extra: 01ce4ad568a5506ba812680e9c1cea2fdbb6e8a8343310c27324cd9d1f4ba9cedb02110000001449d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 953f6df2ba67148fd10ed42514a5c1d42e2056a20c6b575444c36e603354e2c8 0.000600000000 1943629 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": 1454549, "vin": [ { "gen": { "height": 1454539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "953f6df2ba67148fd10ed42514a5c1d42e2056a20c6b575444c36e603354e2c8" } } ], "extra": [ 1, 206, 74, 213, 104, 165, 80, 107, 168, 18, 104, 14, 156, 28, 234, 47, 219, 182, 232, 168, 52, 51, 16, 194, 115, 36, 205, 157, 31, 75, 169, 206, 219, 2, 17, 0, 0, 0, 20, 73, 215, 62, 152, 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: