Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1cff319153450e47beeebaf9dcd2cc7a4b3e144fe4a879d268b3d26e179dca8

Tx prefix hash: f0049f1f08740d6dbb4f6ab110e1c0ff0feb2494c6092f274aac978f9d885d80
Tx public key: ced419a02cd6696bfcc248a9dc30ccc9cb604a85336d24c3b1d674b8dd53dcc7
Timestamp: 1770610526 Timestamp [UTC]: 2026-02-09 04:15:26 Age [y:d:h:m:s]: 00:004:21:16:43
Block: 1473831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 3455 RingCT/type: yes/0
Extra: 01ced419a02cd6696bfcc248a9dc30ccc9cb604a85336d24c3b1d674b8dd53dcc70208e992e8ae62ff42bb

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b5acbf2c9d00d272c89b694b8e2d52df9c79bd9926527f3f33a67c1bd49d0ff5 0.000600000000 1963125 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": 1473841, "vin": [ { "gen": { "height": 1473831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5acbf2c9d00d272c89b694b8e2d52df9c79bd9926527f3f33a67c1bd49d0ff5" } } ], "extra": [ 1, 206, 212, 25, 160, 44, 214, 105, 107, 252, 194, 72, 169, 220, 48, 204, 201, 203, 96, 74, 133, 51, 109, 36, 195, 177, 214, 116, 184, 221, 83, 220, 199, 2, 8, 233, 146, 232, 174, 98, 255, 66, 187 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369