Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c5c46c73a648482b68d6f967aba40a8a1c9e2f0b0f6514786eaa6014862cd1

Tx prefix hash: bc740715c1e3ce3ed420abe294e48f11bef80b186926415a1d97f18854f5ac0b
Tx public key: 285df3e462199452c167a07972067fc8785218433307145432a84e7d98bc6a6a
Timestamp: 1698532349 Timestamp [UTC]: 2023-10-28 22:32:29 Age [y:d:h:m:s]: 02:201:20:45:50
Block: 879789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656314 RingCT/type: yes/0
Extra: 01285df3e462199452c167a07972067fc8785218433307145432a84e7d98bc6a6a021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.000746266314 xmr

stealth address amount amount idx tag
00: 0326d09873ee2a366b8ac5e702a740c6771de884966b45930d6a96a42dde885b 0.000746266314 1335329 of 0 -

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": 879799, "vin": [ { "gen": { "height": 879789 } } ], "vout": [ { "amount": 746266314, "target": { "key": "0326d09873ee2a366b8ac5e702a740c6771de884966b45930d6a96a42dde885b" } } ], "extra": [ 1, 40, 93, 243, 228, 98, 25, 148, 82, 193, 103, 160, 121, 114, 6, 127, 200, 120, 82, 24, 67, 51, 7, 20, 84, 50, 168, 78, 125, 152, 188, 106, 106, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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: