Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80458d8cd3ef3fdab851329a974f3cab1efb87237f17a0fbc1f2a989e9bfb77b

Tx prefix hash: c6591190cefac34dfd4559f5a26bb722772e364ea538c3becfbb8de0ad241982
Tx public key: bfc9475504a67add9bf27e44a7d471ac35bedfff455f7c4f3bbd87393f849909
Timestamp: 1740622952 Timestamp [UTC]: 2025-02-27 02:22:32 Age [y:d:h:m:s]: 01:143:19:45:02
Block: 1228057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355057 RingCT/type: yes/0
Extra: 01bfc9475504a67add9bf27e44a7d471ac35bedfff455f7c4f3bbd87393f84990902110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a612c353853b1c98ba958f8f9655b5efc86abad6c464d97946dbae64e90c136f 0.000600000000 1714934 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": 1228067, "vin": [ { "gen": { "height": 1228057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a612c353853b1c98ba958f8f9655b5efc86abad6c464d97946dbae64e90c136f" } } ], "extra": [ 1, 191, 201, 71, 85, 4, 166, 122, 221, 155, 242, 126, 68, 167, 212, 113, 172, 53, 190, 223, 255, 69, 95, 124, 79, 59, 189, 135, 57, 63, 132, 153, 9, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: