Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6930fbb477208cfdf058721ff03e1f01d554f3cf81e4919bde0f963c29d4ce43

Tx prefix hash: d9f3f1b4280f201b97ec2110a5305b8114e81abfde6bc417024154344cd3b1e3
Tx public key: df428e362e4444bd886621c00f2d94305a40f281568deff8240cc3dcf5fb8ece
Timestamp: 1748560438 Timestamp [UTC]: 2025-05-29 23:13:58 Age [y:d:h:m:s]: 01:171:02:23:27
Block: 1293802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386254 RingCT/type: yes/0
Extra: 01df428e362e4444bd886621c00f2d94305a40f281568deff8240cc3dcf5fb8ece02110000000843846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 467a64e2d3be1b2d1ef5d070f225888f3205c6876db634318424d11e94bffa37 0.000600000000 1781297 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": 1293812, "vin": [ { "gen": { "height": 1293802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "467a64e2d3be1b2d1ef5d070f225888f3205c6876db634318424d11e94bffa37" } } ], "extra": [ 1, 223, 66, 142, 54, 46, 68, 68, 189, 136, 102, 33, 192, 15, 45, 148, 48, 90, 64, 242, 129, 86, 141, 239, 248, 36, 12, 195, 220, 245, 251, 142, 206, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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: