Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44ac0d454bdb1f34e4130f7faae5f63f70cc60d9e5639cdff04bb23c0b2cee54

Tx prefix hash: 2968fe23b4d6580005cf1873ddadbb3b5e2342dff05370af967072656eba9456
Tx public key: bb1aa209cc3ed94a779b1493d9d11144ab99c9bb5d42cb7cc113a0c0ca21a771
Timestamp: 1774243685 Timestamp [UTC]: 2026-03-23 05:28:05 Age [y:d:h:m:s]: 00:238:06:26:21
Block: 1503858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175776 RingCT/type: yes/0
Extra: 01bb1aa209cc3ed94a779b1493d9d11144ab99c9bb5d42cb7cc113a0c0ca21a771021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 16d2009b38762777ca78dcff60f2ecc6c0c14923da9d96d0f02f6cc75e30ab8d 0.000600000000 1993572 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": 1503868, "vin": [ { "gen": { "height": 1503858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16d2009b38762777ca78dcff60f2ecc6c0c14923da9d96d0f02f6cc75e30ab8d" } } ], "extra": [ 1, 187, 26, 162, 9, 204, 62, 217, 74, 119, 155, 20, 147, 217, 209, 17, 68, 171, 153, 201, 187, 93, 66, 203, 124, 193, 19, 160, 192, 202, 33, 167, 113, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: