Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3feabab2aa127e3528704aee84073d0c28171ad1d5d06d63de51bbc74ce9dcd9

Tx prefix hash: 5dece1ea8be844ed7c8a7d3c19174e480e69dc455ac400b26bbe06bf0b0c372a
Tx public key: 28a2390269450cb194d42dbc463f297b4a6b4c093487bf42b05a046a6f12f6b8
Timestamp: 1711895630 Timestamp [UTC]: 2024-03-31 14:33:50 Age [y:d:h:m:s]: 02:043:21:58:27
Block: 990391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543209 RingCT/type: yes/0
Extra: 0128a2390269450cb194d42dbc463f297b4a6b4c093487bf42b05a046a6f12f6b80211000000040011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 31b21c20aabb1b198de4492b77816f34027cf04aae81eeed02b3f2d514401b1b 0.000600000000 1450713 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": 990401, "vin": [ { "gen": { "height": 990391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31b21c20aabb1b198de4492b77816f34027cf04aae81eeed02b3f2d514401b1b" } } ], "extra": [ 1, 40, 162, 57, 2, 105, 69, 12, 177, 148, 212, 45, 188, 70, 63, 41, 123, 74, 107, 76, 9, 52, 135, 191, 66, 176, 90, 4, 106, 111, 18, 246, 184, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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: