Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa2cb67734e56e7c30443efce5442f7c3db3764099f4f2dbec1dbb43e08a682

Tx prefix hash: fd7b519e078a0891e37f8f48a6b78b7d1f878fc8d93e834e7a8b30380a9e2490
Tx public key: 0126cd060d068c1ad14c000224e72327ab9d4878dfe7c60a17d422bbdf3cbdd3
Timestamp: 1743017664 Timestamp [UTC]: 2025-03-26 19:34:24 Age [y:d:h:m:s]: 01:239:10:49:22
Block: 1247882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435341 RingCT/type: yes/0
Extra: 010126cd060d068c1ad14c000224e72327ab9d4878dfe7c60a17d422bbdf3cbdd3021100000003d2e40efd000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aef71b2c45fce59694953e5899f25aee4a2a53bd7fef12c29e1bfb53c90b53bf 0.000600000000 1734909 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": 1247892, "vin": [ { "gen": { "height": 1247882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef71b2c45fce59694953e5899f25aee4a2a53bd7fef12c29e1bfb53c90b53bf" } } ], "extra": [ 1, 1, 38, 205, 6, 13, 6, 140, 26, 209, 76, 0, 2, 36, 231, 35, 39, 171, 157, 72, 120, 223, 231, 198, 10, 23, 212, 34, 187, 223, 60, 189, 211, 2, 17, 0, 0, 0, 3, 210, 228, 14, 253, 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: