Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 016e03aa51776b84bc36fa20c01a7dd4e7f4aa93e04cc98ede140fd0bed63a9f

Tx prefix hash: b01b034b217334bb7087bffd520f5be8b3f25a02abb2d4aeb2b1d1242e39a0dc
Tx public key: 07541705f2c04a53fcf66128e8be88b08df419db2554d20cfa178104134dc913
Timestamp: 1772352379 Timestamp [UTC]: 2026-03-01 08:06:19 Age [y:d:h:m:s]: 00:264:04:05:04
Block: 1488215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194459 RingCT/type: yes/0
Extra: 0107541705f2c04a53fcf66128e8be88b08df419db2554d20cfa178104134dc913021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df70226d50dcf18a14340587ac66e4baff25135e8687b6172fbe7c716d3f90ea 0.000600000000 1977691 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": 1488225, "vin": [ { "gen": { "height": 1488215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df70226d50dcf18a14340587ac66e4baff25135e8687b6172fbe7c716d3f90ea" } } ], "extra": [ 1, 7, 84, 23, 5, 242, 192, 74, 83, 252, 246, 97, 40, 232, 190, 136, 176, 141, 244, 25, 219, 37, 84, 210, 12, 250, 23, 129, 4, 19, 77, 201, 19, 2, 17, 0, 0, 0, 3, 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: