Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 707dd748929135b334e39407224bfa7fbd60d3530a82ae3048ec566f744d3520

Tx prefix hash: 4a8bd112a3375c1ec836e9d267cb713f6131211e0859e5acc6911499974919ed
Tx public key: 4892149888c3b2df6ad4e73c6051c5ef86c849611620545f7c5584bde4da70cc
Timestamp: 1722931417 Timestamp [UTC]: 2024-08-06 08:03:37 Age [y:d:h:m:s]: 02:048:00:46:07
Block: 1081857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559848 RingCT/type: yes/0
Extra: 014892149888c3b2df6ad4e73c6051c5ef86c849611620545f7c5584bde4da70cc021100000001e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0dfba6fc3a9a70d35d13eccb4569db79fd5dd8d81aef253356f0d7730a6dd973 0.000600000000 1555680 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": 1081867, "vin": [ { "gen": { "height": 1081857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dfba6fc3a9a70d35d13eccb4569db79fd5dd8d81aef253356f0d7730a6dd973" } } ], "extra": [ 1, 72, 146, 20, 152, 136, 195, 178, 223, 106, 212, 231, 60, 96, 81, 197, 239, 134, 200, 73, 97, 22, 32, 84, 95, 124, 85, 132, 189, 228, 218, 112, 204, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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: