Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab271b8a4ae281bd93e1324f225c48615fc88f084e60badde3627698cf18258e

Tx prefix hash: f4d368c5ec2d6c1fab61a1ba12f42c2feb7641030c658c5dbf0b9b09e85de670
Tx public key: 161dc362427f54480f25c0f27986985606565926af06f073060c2eced86e2ae8
Timestamp: 1739196752 Timestamp [UTC]: 2025-02-10 14:12:32 Age [y:d:h:m:s]: 01:028:22:55:19
Block: 1216267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279248 RingCT/type: yes/0
Extra: 01161dc362427f54480f25c0f27986985606565926af06f073060c2eced86e2ae80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9158f33ce3ccc7f82cdaf9f590625f2d4f46c5bd7efdf72f137a9174c18e647a 0.000600000000 1703072 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": 1216277, "vin": [ { "gen": { "height": 1216267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9158f33ce3ccc7f82cdaf9f590625f2d4f46c5bd7efdf72f137a9174c18e647a" } } ], "extra": [ 1, 22, 29, 195, 98, 66, 127, 84, 72, 15, 37, 192, 242, 121, 134, 152, 86, 6, 86, 89, 38, 175, 6, 240, 115, 6, 12, 46, 206, 216, 110, 42, 232, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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) | dinastycoin version: tesla-369