Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70bdfd8e921426de7ab1be07db2c7499bdfa2c872c856fe02131bfeedbbe58db

Tx prefix hash: 96e40f3d31f6f54173c21f637a143eb9b3058bdead6e0950c68b8e06732d3141
Tx public key: 65845011fd318f9a23cd9bfb3106644be379fc46ef5fe7d0ae77a12f88909e03
Timestamp: 1756525319 Timestamp [UTC]: 2025-08-30 03:41:59 Age [y:d:h:m:s]: 01:077:13:03:49
Block: 1357413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321612 RingCT/type: yes/0
Extra: 0165845011fd318f9a23cd9bfb3106644be379fc46ef5fe7d0ae77a12f88909e03021100000001ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 551d487ceda5dfba4b22f3a3b50c1163f28fbe71ff56e9a5b91dea8dc73dbb23 0.000600000000 1845422 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": 1357423, "vin": [ { "gen": { "height": 1357413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "551d487ceda5dfba4b22f3a3b50c1163f28fbe71ff56e9a5b91dea8dc73dbb23" } } ], "extra": [ 1, 101, 132, 80, 17, 253, 49, 143, 154, 35, 205, 155, 251, 49, 6, 100, 75, 227, 121, 252, 70, 239, 95, 231, 208, 174, 119, 161, 47, 136, 144, 158, 3, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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: