Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be94e978ea6bc4c432920b7e8abf3e711ca06666f33b91e4989e80d9b7be9d07

Tx prefix hash: dd3322414462ea74cb718b845176471159c0163ec7777695ee4a6d5d4bffd3e4
Tx public key: 162cb94fa9d7795ffafe83e5ab5539348d260514ee0214d2082d150aa600c2b5
Timestamp: 1746980188 Timestamp [UTC]: 2025-05-11 16:16:28 Age [y:d:h:m:s]: 01:003:04:14:41
Block: 1280704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253152 RingCT/type: yes/0
Extra: 01162cb94fa9d7795ffafe83e5ab5539348d260514ee0214d2082d150aa600c2b50211000000091f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e57f0975ae57c907a5fc1546d605830a7e2b365aad06dec9d1320e0e4e8dbcdb 0.000600000000 1768095 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": 1280714, "vin": [ { "gen": { "height": 1280704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e57f0975ae57c907a5fc1546d605830a7e2b365aad06dec9d1320e0e4e8dbcdb" } } ], "extra": [ 1, 22, 44, 185, 79, 169, 215, 121, 95, 250, 254, 131, 229, 171, 85, 57, 52, 141, 38, 5, 20, 238, 2, 20, 210, 8, 45, 21, 10, 166, 0, 194, 181, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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: