Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f7ba23e724e201624bc3fec2615937e236037d88a0c758cb7a49f91920ba23b

Tx prefix hash: de74cef9bbcfd852b90a9125a11444694a420c72439615f1c67692e75723c16d
Tx public key: 19551156b1a4e0fb1cf40109d243214905fd2138545a4e3956a8cb73d5283f23
Timestamp: 1741183078 Timestamp [UTC]: 2025-03-05 13:57:58 Age [y:d:h:m:s]: 00:346:13:19:48
Block: 1232720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245340 RingCT/type: yes/0
Extra: 0119551156b1a4e0fb1cf40109d243214905fd2138545a4e3956a8cb73d5283f230211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 83c4cd1a1d92a817adc831d45ea26c0dc2180ad17c8748d487d5d0bf863b19b5 0.000600000000 1719633 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": 1232730, "vin": [ { "gen": { "height": 1232720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83c4cd1a1d92a817adc831d45ea26c0dc2180ad17c8748d487d5d0bf863b19b5" } } ], "extra": [ 1, 25, 85, 17, 86, 177, 164, 224, 251, 28, 244, 1, 9, 210, 67, 33, 73, 5, 253, 33, 56, 84, 90, 78, 57, 86, 168, 203, 115, 213, 40, 63, 35, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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) | dinastycoin version: tesla-369