Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4cd3342a8c2bc4c7b8f8c297bb81ef18d4081944493a56a706f4e8621462a84

Tx prefix hash: 82fc8f78a3c135db20a891b3a782924b703578ac57e6722131bb47df612cd98c
Tx public key: c4d3d10cab63a0412639eecf86c271ab0fb8f1d431b85d6e5c60d48ef0395ee6
Timestamp: 1759047989 Timestamp [UCT]: 2025-09-28 08:26:29 Age [y:d:h:m:s]: 00:048:21:13:04
Block: 1378163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35001 RingCT/type: yes/0
Extra: 01c4d3d10cab63a0412639eecf86c271ab0fb8f1d431b85d6e5c60d48ef0395ee602110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ac492daf13e566dbab5a63c7373e8057c4b88720a9acfb91a9677c430842f8a 0.600000000000 1866258 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 dinasty-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": 1378173, "vin": [ { "gen": { "height": 1378163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ac492daf13e566dbab5a63c7373e8057c4b88720a9acfb91a9677c430842f8a" } } ], "extra": [ 1, 196, 211, 209, 12, 171, 99, 160, 65, 38, 57, 238, 207, 134, 194, 113, 171, 15, 184, 241, 212, 49, 184, 93, 110, 92, 96, 212, 142, 240, 57, 94, 230, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8