Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3cee7ec31c00e1012a9755efbceda5614b8b94bee5098c08af7f76ab4c4c3d5

Tx prefix hash: ff734e50e6e8e0cbd61410c25a165095c82ad5f109bc1c34973c6c5d28845c30
Tx public key: 8bf9bb74172fd5011ca4c0e365a84581174faae28b33eece93f675c0384477fa
Timestamp: 1774388487 Timestamp [UTC]: 2026-03-24 21:41:27 Age [y:d:h:m:s]: 00:237:05:19:25
Block: 1505057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175041 RingCT/type: yes/0
Extra: 018bf9bb74172fd5011ca4c0e365a84581174faae28b33eece93f675c0384477fa021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d471b4260c8b2ff1d5ff3530e91274c633604bdb99c3139bc6ce1673c311fd1e 0.000600000000 1994789 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": 1505067, "vin": [ { "gen": { "height": 1505057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d471b4260c8b2ff1d5ff3530e91274c633604bdb99c3139bc6ce1673c311fd1e" } } ], "extra": [ 1, 139, 249, 187, 116, 23, 47, 213, 1, 28, 164, 192, 227, 101, 168, 69, 129, 23, 79, 170, 226, 139, 51, 238, 206, 147, 246, 117, 192, 56, 68, 119, 250, 2, 17, 0, 0, 0, 4, 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: