Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5b1e8ba7338b541b89af1fe280897b46d871cb33ff154eea6905edac6713bf

Tx prefix hash: fdda836daf64fa79cd87c4a45e334dce369337b6f66c8a205a8007f2fed0f0f3
Tx public key: f816078da6e8417734182a6d2f71c424fa024f3aa148e0dda907c90d9bb96039
Timestamp: 1772262440 Timestamp [UTC]: 2026-02-28 07:07:20 Age [y:d:h:m:s]: 00:265:22:08:32
Block: 1487463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195722 RingCT/type: yes/0
Extra: 01f816078da6e8417734182a6d2f71c424fa024f3aa148e0dda907c90d9bb96039021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9e7a5d1031957cb4c2a5fd05c3dc807f84bf8f0a226d0bceea44c7d05bcba807 0.000600000000 1976933 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": 1487473, "vin": [ { "gen": { "height": 1487463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7a5d1031957cb4c2a5fd05c3dc807f84bf8f0a226d0bceea44c7d05bcba807" } } ], "extra": [ 1, 248, 22, 7, 141, 166, 232, 65, 119, 52, 24, 42, 109, 47, 113, 196, 36, 250, 2, 79, 58, 161, 72, 224, 221, 169, 7, 201, 13, 155, 185, 96, 57, 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: