Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2948a29b9ac6d2e65fbee4c68fa77cecaceaf3a16881aa3e5ef6cc8c22344ec0

Tx prefix hash: 39f7269bc938e185cef7d33af676971d734ca41f05242500b1e256f0447a41ff
Tx public key: 995c297deb200d7b4d9c8acc052120f84941cac76dccc2338a35adbe5cbac352
Timestamp: 1740832564 Timestamp [UTC]: 2025-03-01 12:36:04 Age [y:d:h:m:s]: 01:264:16:59:29
Block: 1229803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453395 RingCT/type: yes/0
Extra: 01995c297deb200d7b4d9c8acc052120f84941cac76dccc2338a35adbe5cbac35202110000000e007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 90d78f1f7764d3c2d8694a8ccd7a7713ff9f08e943f486cc7c9158a89d506182 0.000600000000 1716692 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": 1229813, "vin": [ { "gen": { "height": 1229803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90d78f1f7764d3c2d8694a8ccd7a7713ff9f08e943f486cc7c9158a89d506182" } } ], "extra": [ 1, 153, 92, 41, 125, 235, 32, 13, 123, 77, 156, 138, 204, 5, 33, 32, 248, 73, 65, 202, 199, 109, 204, 194, 51, 138, 53, 173, 190, 92, 186, 195, 82, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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: