Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7004c2a2f0e7eb8ffc6b3dd7daef7b7ce731d3886ad01189cf1385766558b786

Tx prefix hash: 44c6863b37bda3d61ed058a2ce335d7e45871a18f4ac03925314eb98279b9794
Tx public key: bf02a339593f9151a6678c0bd5da8af59023b68594b0080963fa9b49e046a08b
Timestamp: 1748288513 Timestamp [UTC]: 2025-05-26 19:41:53 Age [y:d:h:m:s]: 00:351:08:32:01
Block: 1291538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241048 RingCT/type: yes/0
Extra: 01bf02a339593f9151a6678c0bd5da8af59023b68594b0080963fa9b49e046a08b021100000002d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5f668d3b67d575e4e0fdb96838339686642727ae628454d15e9623cf590f6019 0.000600000000 1779009 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": 1291548, "vin": [ { "gen": { "height": 1291538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f668d3b67d575e4e0fdb96838339686642727ae628454d15e9623cf590f6019" } } ], "extra": [ 1, 191, 2, 163, 57, 89, 63, 145, 81, 166, 103, 140, 11, 213, 218, 138, 245, 144, 35, 182, 133, 148, 176, 8, 9, 99, 250, 155, 73, 224, 70, 160, 139, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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: